[INFO] fetching crate hyprland 0.4.0-beta.2...
[INFO] checking hyprland-0.4.0-beta.2 against master#82310651b93a594a3fd69015e1562186a080d94c for pr-145770
[INFO] extracting crate hyprland 0.4.0-beta.2 into /workspace/builds/worker-6-tc1/source
[INFO] started tweaking crates.io crate hyprland 0.4.0-beta.2
[INFO] removed 0 missing examples
[INFO] finished tweaking crates.io crate hyprland 0.4.0-beta.2
[INFO] tweaked toml for crates.io crate hyprland 0.4.0-beta.2 written to /workspace/builds/worker-6-tc1/source/Cargo.toml
[INFO] validating manifest of crates.io crate hyprland 0.4.0-beta.2 on toolchain 82310651b93a594a3fd69015e1562186a080d94c
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+82310651b93a594a3fd69015e1562186a080d94c" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate crates.io crate hyprland 0.4.0-beta.2 already has a lockfile, it will not be regenerated
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+82310651b93a594a3fd69015e1562186a080d94c" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded unicode-xid v0.2.5
[INFO] [stderr]   Downloaded hyprland-macros v0.4.0-beta.2
[INFO] [stderr]   Downloaded zerocopy-derive v0.7.33
[INFO] [stderr]   Downloaded async-channel v2.2.1
[INFO] [stderr]   Downloaded blocking v1.6.0
[INFO] [stderr]   Downloaded value-bag v1.9.0
[INFO] [stderr]   Downloaded zerocopy v0.7.33
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+82310651b93a594a3fd69015e1562186a080d94c" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 3cf0038c8f2c592bf6c2e821a7e196e1bc90993ba642025ef80f5d5810c42c10
[INFO] running `Command { std: "docker" "start" "-a" "3cf0038c8f2c592bf6c2e821a7e196e1bc90993ba642025ef80f5d5810c42c10", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "3cf0038c8f2c592bf6c2e821a7e196e1bc90993ba642025ef80f5d5810c42c10", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "3cf0038c8f2c592bf6c2e821a7e196e1bc90993ba642025ef80f5d5810c42c10", kill_on_drop: false }`
[INFO] [stdout] 3cf0038c8f2c592bf6c2e821a7e196e1bc90993ba642025ef80f5d5810c42c10
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+82310651b93a594a3fd69015e1562186a080d94c" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 1e617469601fe288287862122df2840cd95402d7b76760db284e3a0da2dad7e5
[INFO] running `Command { std: "docker" "start" "-a" "1e617469601fe288287862122df2840cd95402d7b76760db284e3a0da2dad7e5", kill_on_drop: false }`
[INFO] [stderr]    Compiling proc-macro2 v1.0.84
[INFO] [stderr]    Compiling unicode-ident v1.0.12
[INFO] [stderr]    Compiling libc v0.2.154
[INFO] [stderr]    Compiling serde v1.0.215
[INFO] [stderr]    Compiling siphasher v0.3.11
[INFO] [stderr]    Compiling rand_core v0.6.4
[INFO] [stderr]    Compiling version_check v0.9.4
[INFO] [stderr]    Compiling autocfg v1.3.0
[INFO] [stderr]    Compiling phf_shared v0.11.2
[INFO] [stderr]    Compiling rand v0.8.5
[INFO] [stderr]     Checking pin-project-lite v0.2.14
[INFO] [stderr]    Compiling unicode-xid v0.2.5
[INFO] [stderr]     Checking futures-core v0.3.30
[INFO] [stderr]    Compiling serde_json v1.0.133
[INFO] [stderr]    Compiling paste v1.0.15
[INFO] [stderr]     Checking ryu v1.0.18
[INFO] [stderr]    Compiling ahash v0.8.11
[INFO] [stderr]     Checking zerocopy v0.7.33
[INFO] [stderr]    Compiling num-traits v0.2.19
[INFO] [stderr]     Checking memchr v2.7.2
[INFO] [stderr]    Compiling phf_generator v0.11.2
[INFO] [stderr]     Checking once_cell v1.19.0
[INFO] [stderr]     Checking cfg-if v1.0.0
[INFO] [stderr]     Checking bytes v1.6.0
[INFO] [stderr]     Checking itoa v1.0.11
[INFO] [stderr]     Checking futures-lite v2.3.0
[INFO] [stderr]     Checking either v1.13.0
[INFO] [stderr]    Compiling quote v1.0.37
[INFO] [stderr]     Checking mio v1.0.2
[INFO] [stderr]     Checking socket2 v0.5.7
[INFO] [stderr]    Compiling syn v2.0.87
[INFO] [stderr]    Compiling serde_derive v1.0.215
[INFO] [stderr]    Compiling tokio-macros v2.4.0
[INFO] [stderr]    Compiling derive_more-impl v1.0.0
[INFO] [stderr]    Compiling phf_macros v0.11.2
[INFO] [stderr]    Compiling async-stream-impl v0.3.5
[INFO] [stderr]    Compiling serde_repr v0.1.19
[INFO] [stderr]    Compiling hyprland-macros v0.4.0-beta.2
[INFO] [stderr]     Checking async-stream v0.3.5
[INFO] [stderr]     Checking phf v0.11.2
[INFO] [stderr]     Checking tokio v1.40.0
[INFO] [stderr]     Checking derive_more v1.0.0
[INFO] [stderr]     Checking hyprland v0.4.0-beta.2 (/opt/rustwide/workdir)
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:28:29
[INFO] [stdout]     |
[INFO] [stdout] 28  |                   pub fn iter(&self) -> std::slice::Iter<$holding_type> {
[INFO] [stdout]     |                               ^^^^^     ------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                               |
[INFO] [stdout]     |                               the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:151:1
[INFO] [stdout]     |
[INFO] [stdout] 151 | / create_data_struct!(
[INFO] [stdout] 152 | |     vector,
[INFO] [stdout] 153 | |     name: Monitors,
[INFO] [stdout] 154 | |     command: DataCommands::Monitors,
[INFO] [stdout] 155 | |     holding_type: Monitor,
[INFO] [stdout] 156 | |     doc: "This struct holds a vector of monitors"
[INFO] [stdout] 157 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 28  |                 pub fn iter(&self) -> std::slice::Iter<'_, $holding_type> {
[INFO] [stdout]     |                                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:33:33
[INFO] [stdout]     |
[INFO] [stdout] 33  |                   pub fn iter_mut(&mut self) -> std::slice::IterMut<$holding_type> {
[INFO] [stdout]     |                                   ^^^^^^^^^     ---------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                                   |
[INFO] [stdout]     |                                   the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:151:1
[INFO] [stdout]     |
[INFO] [stdout] 151 | / create_data_struct!(
[INFO] [stdout] 152 | |     vector,
[INFO] [stdout] 153 | |     name: Monitors,
[INFO] [stdout] 154 | |     command: DataCommands::Monitors,
[INFO] [stdout] 155 | |     holding_type: Monitor,
[INFO] [stdout] 156 | |     doc: "This struct holds a vector of monitors"
[INFO] [stdout] 157 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 33  |                 pub fn iter_mut(&mut self) -> std::slice::IterMut<'_, $holding_type> {
[INFO] [stdout]     |                                                                   +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:28:29
[INFO] [stdout]     |
[INFO] [stdout] 28  |                   pub fn iter(&self) -> std::slice::Iter<$holding_type> {
[INFO] [stdout]     |                               ^^^^^     ------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                               |
[INFO] [stdout]     |                               the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:197:1
[INFO] [stdout]     |
[INFO] [stdout] 197 | / create_data_struct!(
[INFO] [stdout] 198 | |     vector,
[INFO] [stdout] 199 | |     name: Workspaces,
[INFO] [stdout] 200 | |     command: DataCommands::Workspaces,
[INFO] [stdout] 201 | |     holding_type: Workspace,
[INFO] [stdout] 202 | |     doc: "This type provides a vector of workspaces"
[INFO] [stdout] 203 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 28  |                 pub fn iter(&self) -> std::slice::Iter<'_, $holding_type> {
[INFO] [stdout]     |                                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:33:33
[INFO] [stdout]     |
[INFO] [stdout] 33  |                   pub fn iter_mut(&mut self) -> std::slice::IterMut<$holding_type> {
[INFO] [stdout]     |                                   ^^^^^^^^^     ---------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                                   |
[INFO] [stdout]     |                                   the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:197:1
[INFO] [stdout]     |
[INFO] [stdout] 197 | / create_data_struct!(
[INFO] [stdout] 198 | |     vector,
[INFO] [stdout] 199 | |     name: Workspaces,
[INFO] [stdout] 200 | |     command: DataCommands::Workspaces,
[INFO] [stdout] 201 | |     holding_type: Workspace,
[INFO] [stdout] 202 | |     doc: "This type provides a vector of workspaces"
[INFO] [stdout] 203 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 33  |                 pub fn iter_mut(&mut self) -> std::slice::IterMut<'_, $holding_type> {
[INFO] [stdout]     |                                                                   +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:28:29
[INFO] [stdout]     |
[INFO] [stdout] 28  |                   pub fn iter(&self) -> std::slice::Iter<$holding_type> {
[INFO] [stdout]     |                               ^^^^^     ------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                               |
[INFO] [stdout]     |                               the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:293:1
[INFO] [stdout]     |
[INFO] [stdout] 293 | / create_data_struct!(
[INFO] [stdout] 294 | |     vector,
[INFO] [stdout] 295 | |     name: Clients,
[INFO] [stdout] 296 | |     command: DataCommands::Clients,
[INFO] [stdout] 297 | |     holding_type: Client,
[INFO] [stdout] 298 | |     doc: "This struct holds a vector of clients"
[INFO] [stdout] 299 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 28  |                 pub fn iter(&self) -> std::slice::Iter<'_, $holding_type> {
[INFO] [stdout]     |                                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:33:33
[INFO] [stdout]     |
[INFO] [stdout] 33  |                   pub fn iter_mut(&mut self) -> std::slice::IterMut<$holding_type> {
[INFO] [stdout]     |                                   ^^^^^^^^^     ---------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                                   |
[INFO] [stdout]     |                                   the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:293:1
[INFO] [stdout]     |
[INFO] [stdout] 293 | / create_data_struct!(
[INFO] [stdout] 294 | |     vector,
[INFO] [stdout] 295 | |     name: Clients,
[INFO] [stdout] 296 | |     command: DataCommands::Clients,
[INFO] [stdout] 297 | |     holding_type: Client,
[INFO] [stdout] 298 | |     doc: "This struct holds a vector of clients"
[INFO] [stdout] 299 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 33  |                 pub fn iter_mut(&mut self) -> std::slice::IterMut<'_, $holding_type> {
[INFO] [stdout]     |                                                                   +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:78:29
[INFO] [stdout]     |
[INFO] [stdout] 78  |                   pub fn iter(&self) -> std::collections::hash_map::Iter<$key, $value> {
[INFO] [stdout]     |                               ^^^^^     ---------------------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                               |
[INFO] [stdout]     |                               the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:325:1
[INFO] [stdout]     |
[INFO] [stdout] 325 | / implement_iterators!(
[INFO] [stdout] 326 | |     table,
[INFO] [stdout] 327 | |     name: LayerDisplay,
[INFO] [stdout] 328 | |     iterated_field: levels,
[INFO] [stdout] 329 | |     key: String,
[INFO] [stdout] 330 | |     value: Vec<LayerClient>,
[INFO] [stdout] 331 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 78  |                 pub fn iter(&self) -> std::collections::hash_map::Iter<'_, $key, $value> {
[INFO] [stdout]     |                                                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:83:33
[INFO] [stdout]     |
[INFO] [stdout] 83  |                   pub fn iter_mut(&mut self) -> std::collections::hash_map::IterMut<$key, $value> {
[INFO] [stdout]     |                                   ^^^^^^^^^     ------------------------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                                   |
[INFO] [stdout]     |                                   the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:325:1
[INFO] [stdout]     |
[INFO] [stdout] 325 | / implement_iterators!(
[INFO] [stdout] 326 | |     table,
[INFO] [stdout] 327 | |     name: LayerDisplay,
[INFO] [stdout] 328 | |     iterated_field: levels,
[INFO] [stdout] 329 | |     key: String,
[INFO] [stdout] 330 | |     value: Vec<LayerClient>,
[INFO] [stdout] 331 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 pub fn iter_mut(&mut self) -> std::collections::hash_map::IterMut<'_, $key, $value> {
[INFO] [stdout]     |                                                                                   +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:78:29
[INFO] [stdout]     |
[INFO] [stdout] 78  |                   pub fn iter(&self) -> std::collections::hash_map::Iter<$key, $value> {
[INFO] [stdout]     |                               ^^^^^     ---------------------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                               |
[INFO] [stdout]     |                               the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:333:1
[INFO] [stdout]     |
[INFO] [stdout] 333 | / create_data_struct!(
[INFO] [stdout] 334 | |     table,
[INFO] [stdout] 335 | |     name: Layers,
[INFO] [stdout] 336 | |     command: DataCommands::Layers,
[INFO] [stdout] ...   |
[INFO] [stdout] 339 | |     doc: "This struct holds a hashmap of all current displays, and their layer surfaces"
[INFO] [stdout] 340 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 78  |                 pub fn iter(&self) -> std::collections::hash_map::Iter<'_, $key, $value> {
[INFO] [stdout]     |                                                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:83:33
[INFO] [stdout]     |
[INFO] [stdout] 83  |                   pub fn iter_mut(&mut self) -> std::collections::hash_map::IterMut<$key, $value> {
[INFO] [stdout]     |                                   ^^^^^^^^^     ------------------------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                                   |
[INFO] [stdout]     |                                   the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:333:1
[INFO] [stdout]     |
[INFO] [stdout] 333 | / create_data_struct!(
[INFO] [stdout] 334 | |     table,
[INFO] [stdout] 335 | |     name: Layers,
[INFO] [stdout] 336 | |     command: DataCommands::Layers,
[INFO] [stdout] ...   |
[INFO] [stdout] 339 | |     doc: "This struct holds a hashmap of all current displays, and their layer surfaces"
[INFO] [stdout] 340 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 pub fn iter_mut(&mut self) -> std::collections::hash_map::IterMut<'_, $key, $value> {
[INFO] [stdout]     |                                                                                   +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:28:29
[INFO] [stdout]     |
[INFO] [stdout] 28  |                   pub fn iter(&self) -> std::slice::Iter<$holding_type> {
[INFO] [stdout]     |                               ^^^^^     ------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                               |
[INFO] [stdout]     |                               the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:490:1
[INFO] [stdout]     |
[INFO] [stdout] 490 | / create_data_struct!(
[INFO] [stdout] 491 | |     vector,
[INFO] [stdout] 492 | |     name: Binds,
[INFO] [stdout] 493 | |     command: DataCommands::Binds,
[INFO] [stdout] 494 | |     holding_type: Bind,
[INFO] [stdout] 495 | |     doc: "This struct holds a vector of binds"
[INFO] [stdout] 496 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 28  |                 pub fn iter(&self) -> std::slice::Iter<'_, $holding_type> {
[INFO] [stdout]     |                                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:33:33
[INFO] [stdout]     |
[INFO] [stdout] 33  |                   pub fn iter_mut(&mut self) -> std::slice::IterMut<$holding_type> {
[INFO] [stdout]     |                                   ^^^^^^^^^     ---------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                                   |
[INFO] [stdout]     |                                   the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:490:1
[INFO] [stdout]     |
[INFO] [stdout] 490 | / create_data_struct!(
[INFO] [stdout] 491 | |     vector,
[INFO] [stdout] 492 | |     name: Binds,
[INFO] [stdout] 493 | |     command: DataCommands::Binds,
[INFO] [stdout] 494 | |     holding_type: Bind,
[INFO] [stdout] 495 | |     doc: "This struct holds a vector of binds"
[INFO] [stdout] 496 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 33  |                 pub fn iter_mut(&mut self) -> std::slice::IterMut<'_, $holding_type> {
[INFO] [stdout]     |                                                                   +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:28:29
[INFO] [stdout]     |
[INFO] [stdout] 28  |                   pub fn iter(&self) -> std::slice::Iter<$holding_type> {
[INFO] [stdout]     |                               ^^^^^     ------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                               |
[INFO] [stdout]     |                               the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:712:1
[INFO] [stdout]     |
[INFO] [stdout] 712 | / create_data_struct!(
[INFO] [stdout] 713 | |     vector,
[INFO] [stdout] 714 | |     name: WorkspaceRules,
[INFO] [stdout] 715 | |     command: DataCommands::WorkspaceRules,
[INFO] [stdout] 716 | |     holding_type: WorkspaceRuleset,
[INFO] [stdout] 717 | |     doc: "This struct holds a vector of workspace rules per workspace"
[INFO] [stdout] 718 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 28  |                 pub fn iter(&self) -> std::slice::Iter<'_, $holding_type> {
[INFO] [stdout]     |                                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:33:33
[INFO] [stdout]     |
[INFO] [stdout] 33  |                   pub fn iter_mut(&mut self) -> std::slice::IterMut<$holding_type> {
[INFO] [stdout]     |                                   ^^^^^^^^^     ---------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                                   |
[INFO] [stdout]     |                                   the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:712:1
[INFO] [stdout]     |
[INFO] [stdout] 712 | / create_data_struct!(
[INFO] [stdout] 713 | |     vector,
[INFO] [stdout] 714 | |     name: WorkspaceRules,
[INFO] [stdout] 715 | |     command: DataCommands::WorkspaceRules,
[INFO] [stdout] 716 | |     holding_type: WorkspaceRuleset,
[INFO] [stdout] 717 | |     doc: "This struct holds a vector of workspace rules per workspace"
[INFO] [stdout] 718 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 33  |                 pub fn iter_mut(&mut self) -> std::slice::IterMut<'_, $holding_type> {
[INFO] [stdout]     |                                                                   +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused `Result` that must be used
[INFO] [stdout]   --> examples/bind.rs:14:5
[INFO] [stdout]    |
[INFO] [stdout] 14 |     hyprland::bind!(l | CTRL ALT, Key, "Delete" => Exec, "sudo reboot"); // Reboot including from lock screen
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: this `Result` may be an `Err` variant, which should be handled
[INFO] [stdout]    = note: `#[warn(unused_must_use)]` on by default
[INFO] [stdout]    = note: this warning originates in the macro `hyprland::bind` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `add_active_window_change_handler` found for struct `AsyncEventListener` in the current scope
[INFO] [stdout]   --> examples/events_async.rs:13:20
[INFO] [stdout]    |
[INFO] [stdout] 13 |     event_listener.add_active_window_change_handler(async_closure! {
[INFO] [stdout]    |     ---------------^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout] help: there is a method `add_active_window_changed_handler` with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 13 |     event_listener.add_active_window_changed_handler(async_closure! {
[INFO] [stdout]    |                                            +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused `Result` that must be used
[INFO] [stdout]   --> examples/bind.rs:15:5
[INFO] [stdout]    |
[INFO] [stdout] 15 |     hyprland::bind!(e | SUPER, Key, "C" => KillActiveWindow); // Kill all your windows  
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: this `Result` may be an `Err` variant, which should be handled
[INFO] [stdout]    = note: this warning originates in the macro `hyprland::bind` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `add_fullscreen_state_change_handler` found for struct `AsyncEventListener` in the current scope
[INFO] [stdout]   --> examples/events_async.rs:17:20
[INFO] [stdout]    |
[INFO] [stdout] 17 |     event_listener.add_fullscreen_state_change_handler(async_closure! {
[INFO] [stdout]    |     ---------------^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout] help: there is a method `add_fullscreen_state_changed_handler` with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 17 |     event_listener.add_fullscreen_state_changed_handler(async_closure! {
[INFO] [stdout]    |                                               +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `add_active_monitor_change_handler` found for struct `AsyncEventListener` in the current scope
[INFO] [stdout]   --> examples/events_async.rs:21:20
[INFO] [stdout]    |
[INFO] [stdout] 21 |     event_listener.add_active_monitor_change_handler(async_closure! {
[INFO] [stdout]    |     ---------------^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout] help: there is a method `add_active_monitor_changed_handler` with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 21 |     event_listener.add_active_monitor_changed_handler(async_closure! {
[INFO] [stdout]    |                                             +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `add_workspace_change_handler` found for struct `AsyncEventListener` in the current scope
[INFO] [stdout]   --> examples/events_async.rs:26:20
[INFO] [stdout]    |
[INFO] [stdout] 26 |     event_listener.add_workspace_change_handler(async_closure! {
[INFO] [stdout]    |     ---------------^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout] help: there is a method `add_workspace_changed_handler` with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 26 |     event_listener.add_workspace_changed_handler(async_closure! {
[INFO] [stdout]    |                                        +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `hyprland` (example "events_async") due to 4 previous errors
[INFO] [stdout] For more information about this error, try `rustc --explain E0599`.
[INFO] [stdout] 
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] error[E0599]: no method named `add_active_window_change_handler` found for struct `EventListener` in the current scope
[INFO] [stdout]   --> examples/events.rs:11:20
[INFO] [stdout]    |
[INFO] [stdout] 11 |     event_listener.add_active_window_change_handler(|data| println!("{data:#?}"));
[INFO] [stdout]    |                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout] help: there is a method `add_active_window_changed_handler` with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 11 |     event_listener.add_active_window_changed_handler(|data| println!("{data:#?}"));
[INFO] [stdout]    |                                            +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `add_fullscreen_state_change_handler` found for struct `EventListener` in the current scope
[INFO] [stdout]   --> examples/events.rs:12:20
[INFO] [stdout]    |
[INFO] [stdout] 12 |     event_listener.add_fullscreen_state_change_handler(
[INFO] [stdout]    |     ---------------^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout] help: there is a method `add_fullscreen_state_changed_handler` with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 12 |     event_listener.add_fullscreen_state_changed_handler(
[INFO] [stdout]    |                                               +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:28:29
[INFO] [stdout]     |
[INFO] [stdout] 28  |                   pub fn iter(&self) -> std::slice::Iter<$holding_type> {
[INFO] [stdout]     |                               ^^^^^     ------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                               |
[INFO] [stdout]     |                               the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:151:1
[INFO] [stdout]     |
[INFO] [stdout] 151 | / create_data_struct!(
[INFO] [stdout] 152 | |     vector,
[INFO] [stdout] 153 | |     name: Monitors,
[INFO] [stdout] 154 | |     command: DataCommands::Monitors,
[INFO] [stdout] 155 | |     holding_type: Monitor,
[INFO] [stdout] 156 | |     doc: "This struct holds a vector of monitors"
[INFO] [stdout] 157 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 28  |                 pub fn iter(&self) -> std::slice::Iter<'_, $holding_type> {
[INFO] [stdout]     |                                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:33:33
[INFO] [stdout]     |
[INFO] [stdout] 33  |                   pub fn iter_mut(&mut self) -> std::slice::IterMut<$holding_type> {
[INFO] [stdout]     |                                   ^^^^^^^^^     ---------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                                   |
[INFO] [stdout]     |                                   the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:151:1
[INFO] [stdout]     |
[INFO] [stdout] 151 | / create_data_struct!(
[INFO] [stdout] 152 | |     vector,
[INFO] [stdout] 153 | |     name: Monitors,
[INFO] [stdout] 154 | |     command: DataCommands::Monitors,
[INFO] [stdout] 155 | |     holding_type: Monitor,
[INFO] [stdout] 156 | |     doc: "This struct holds a vector of monitors"
[INFO] [stdout] 157 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 33  |                 pub fn iter_mut(&mut self) -> std::slice::IterMut<'_, $holding_type> {
[INFO] [stdout]     |                                                                   +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:28:29
[INFO] [stdout]     |
[INFO] [stdout] 28  |                   pub fn iter(&self) -> std::slice::Iter<$holding_type> {
[INFO] [stdout]     |                               ^^^^^     ------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                               |
[INFO] [stdout]     |                               the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:197:1
[INFO] [stdout]     |
[INFO] [stdout] 197 | / create_data_struct!(
[INFO] [stdout] 198 | |     vector,
[INFO] [stdout] 199 | |     name: Workspaces,
[INFO] [stdout] 200 | |     command: DataCommands::Workspaces,
[INFO] [stdout] 201 | |     holding_type: Workspace,
[INFO] [stdout] 202 | |     doc: "This type provides a vector of workspaces"
[INFO] [stdout] 203 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 28  |                 pub fn iter(&self) -> std::slice::Iter<'_, $holding_type> {
[INFO] [stdout]     |                                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:33:33
[INFO] [stdout]     |
[INFO] [stdout] 33  |                   pub fn iter_mut(&mut self) -> std::slice::IterMut<$holding_type> {
[INFO] [stdout]     |                                   ^^^^^^^^^     ---------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                                   |
[INFO] [stdout]     |                                   the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:197:1
[INFO] [stdout]     |
[INFO] [stdout] 197 | / create_data_struct!(
[INFO] [stdout] 198 | |     vector,
[INFO] [stdout] 199 | |     name: Workspaces,
[INFO] [stdout] 200 | |     command: DataCommands::Workspaces,
[INFO] [stdout] 201 | |     holding_type: Workspace,
[INFO] [stdout] 202 | |     doc: "This type provides a vector of workspaces"
[INFO] [stdout] 203 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 33  |                 pub fn iter_mut(&mut self) -> std::slice::IterMut<'_, $holding_type> {
[INFO] [stdout]     |                                                                   +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:28:29
[INFO] [stdout]     |
[INFO] [stdout] 28  |                   pub fn iter(&self) -> std::slice::Iter<$holding_type> {
[INFO] [stdout]     |                               ^^^^^     ------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                               |
[INFO] [stdout]     |                               the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:293:1
[INFO] [stdout]     |
[INFO] [stdout] 293 | / create_data_struct!(
[INFO] [stdout] 294 | |     vector,
[INFO] [stdout] 295 | |     name: Clients,
[INFO] [stdout] 296 | |     command: DataCommands::Clients,
[INFO] [stdout] 297 | |     holding_type: Client,
[INFO] [stdout] 298 | |     doc: "This struct holds a vector of clients"
[INFO] [stdout] 299 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 28  |                 pub fn iter(&self) -> std::slice::Iter<'_, $holding_type> {
[INFO] [stdout]     |                                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:33:33
[INFO] [stdout]     |
[INFO] [stdout] 33  |                   pub fn iter_mut(&mut self) -> std::slice::IterMut<$holding_type> {
[INFO] [stdout]     |                                   ^^^^^^^^^     ---------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                                   |
[INFO] [stdout]     |                                   the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:293:1
[INFO] [stdout]     |
[INFO] [stdout] 293 | / create_data_struct!(
[INFO] [stdout] 294 | |     vector,
[INFO] [stdout] 295 | |     name: Clients,
[INFO] [stdout] 296 | |     command: DataCommands::Clients,
[INFO] [stdout] 297 | |     holding_type: Client,
[INFO] [stdout] 298 | |     doc: "This struct holds a vector of clients"
[INFO] [stdout] 299 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 33  |                 pub fn iter_mut(&mut self) -> std::slice::IterMut<'_, $holding_type> {
[INFO] [stdout]     |                                                                   +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:78:29
[INFO] [stdout]     |
[INFO] [stdout] 78  |                   pub fn iter(&self) -> std::collections::hash_map::Iter<$key, $value> {
[INFO] [stdout]     |                               ^^^^^     ---------------------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                               |
[INFO] [stdout]     |                               the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:325:1
[INFO] [stdout]     |
[INFO] [stdout] 325 | / implement_iterators!(
[INFO] [stdout] 326 | |     table,
[INFO] [stdout] 327 | |     name: LayerDisplay,
[INFO] [stdout] 328 | |     iterated_field: levels,
[INFO] [stdout] 329 | |     key: String,
[INFO] [stdout] 330 | |     value: Vec<LayerClient>,
[INFO] [stdout] 331 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 78  |                 pub fn iter(&self) -> std::collections::hash_map::Iter<'_, $key, $value> {
[INFO] [stdout]     |                                                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:83:33
[INFO] [stdout]     |
[INFO] [stdout] 83  |                   pub fn iter_mut(&mut self) -> std::collections::hash_map::IterMut<$key, $value> {
[INFO] [stdout]     |                                   ^^^^^^^^^     ------------------------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                                   |
[INFO] [stdout]     |                                   the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:325:1
[INFO] [stdout]     |
[INFO] [stdout] 325 | / implement_iterators!(
[INFO] [stdout] 326 | |     table,
[INFO] [stdout] 327 | |     name: LayerDisplay,
[INFO] [stdout] 328 | |     iterated_field: levels,
[INFO] [stdout] 329 | |     key: String,
[INFO] [stdout] 330 | |     value: Vec<LayerClient>,
[INFO] [stdout] 331 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 pub fn iter_mut(&mut self) -> std::collections::hash_map::IterMut<'_, $key, $value> {
[INFO] [stdout]     |                                                                                   +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:78:29
[INFO] [stdout]     |
[INFO] [stdout] 78  |                   pub fn iter(&self) -> std::collections::hash_map::Iter<$key, $value> {
[INFO] [stdout]     |                               ^^^^^     ---------------------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                               |
[INFO] [stdout]     |                               the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:333:1
[INFO] [stdout]     |
[INFO] [stdout] 333 | / create_data_struct!(
[INFO] [stdout] 334 | |     table,
[INFO] [stdout] 335 | |     name: Layers,
[INFO] [stdout] 336 | |     command: DataCommands::Layers,
[INFO] [stdout] ...   |
[INFO] [stdout] 339 | |     doc: "This struct holds a hashmap of all current displays, and their layer surfaces"
[INFO] [stdout] 340 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 78  |                 pub fn iter(&self) -> std::collections::hash_map::Iter<'_, $key, $value> {
[INFO] [stdout]     |                                                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:83:33
[INFO] [stdout]     |
[INFO] [stdout] 83  |                   pub fn iter_mut(&mut self) -> std::collections::hash_map::IterMut<$key, $value> {
[INFO] [stdout]     |                                   ^^^^^^^^^     ------------------------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                                   |
[INFO] [stdout]     |                                   the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:333:1
[INFO] [stdout]     |
[INFO] [stdout] 333 | / create_data_struct!(
[INFO] [stdout] 334 | |     table,
[INFO] [stdout] 335 | |     name: Layers,
[INFO] [stdout] 336 | |     command: DataCommands::Layers,
[INFO] [stdout] ...   |
[INFO] [stdout] 339 | |     doc: "This struct holds a hashmap of all current displays, and their layer surfaces"
[INFO] [stdout] 340 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 pub fn iter_mut(&mut self) -> std::collections::hash_map::IterMut<'_, $key, $value> {
[INFO] [stdout]     |                                                                                   +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:28:29
[INFO] [stdout]     |
[INFO] [stdout] 28  |                   pub fn iter(&self) -> std::slice::Iter<$holding_type> {
[INFO] [stdout]     |                               ^^^^^     ------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                               |
[INFO] [stdout]     |                               the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:490:1
[INFO] [stdout]     |
[INFO] [stdout] 490 | / create_data_struct!(
[INFO] [stdout] 491 | |     vector,
[INFO] [stdout] 492 | |     name: Binds,
[INFO] [stdout] 493 | |     command: DataCommands::Binds,
[INFO] [stdout] 494 | |     holding_type: Bind,
[INFO] [stdout] 495 | |     doc: "This struct holds a vector of binds"
[INFO] [stdout] 496 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 28  |                 pub fn iter(&self) -> std::slice::Iter<'_, $holding_type> {
[INFO] [stdout]     |                                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:33:33
[INFO] [stdout]     |
[INFO] [stdout] 33  |                   pub fn iter_mut(&mut self) -> std::slice::IterMut<$holding_type> {
[INFO] [stdout]     |                                   ^^^^^^^^^     ---------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                                   |
[INFO] [stdout]     |                                   the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:490:1
[INFO] [stdout]     |
[INFO] [stdout] 490 | / create_data_struct!(
[INFO] [stdout] 491 | |     vector,
[INFO] [stdout] 492 | |     name: Binds,
[INFO] [stdout] 493 | |     command: DataCommands::Binds,
[INFO] [stdout] 494 | |     holding_type: Bind,
[INFO] [stdout] 495 | |     doc: "This struct holds a vector of binds"
[INFO] [stdout] 496 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 33  |                 pub fn iter_mut(&mut self) -> std::slice::IterMut<'_, $holding_type> {
[INFO] [stdout]     |                                                                   +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:28:29
[INFO] [stdout]     |
[INFO] [stdout] 28  |                   pub fn iter(&self) -> std::slice::Iter<$holding_type> {
[INFO] [stdout]     |                               ^^^^^     ------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                               |
[INFO] [stdout]     |                               the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:712:1
[INFO] [stdout]     |
[INFO] [stdout] 712 | / create_data_struct!(
[INFO] [stdout] 713 | |     vector,
[INFO] [stdout] 714 | |     name: WorkspaceRules,
[INFO] [stdout] 715 | |     command: DataCommands::WorkspaceRules,
[INFO] [stdout] 716 | |     holding_type: WorkspaceRuleset,
[INFO] [stdout] 717 | |     doc: "This struct holds a vector of workspace rules per workspace"
[INFO] [stdout] 718 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 28  |                 pub fn iter(&self) -> std::slice::Iter<'_, $holding_type> {
[INFO] [stdout]     |                                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/data/macros.rs:33:33
[INFO] [stdout]     |
[INFO] [stdout] 33  |                   pub fn iter_mut(&mut self) -> std::slice::IterMut<$holding_type> {
[INFO] [stdout]     |                                   ^^^^^^^^^     ---------------------------------- the same lifetime is hidden here
[INFO] [stdout]     |                                   |
[INFO] [stdout]     |                                   the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/data/regular.rs:712:1
[INFO] [stdout]     |
[INFO] [stdout] 712 | / create_data_struct!(
[INFO] [stdout] 713 | |     vector,
[INFO] [stdout] 714 | |     name: WorkspaceRules,
[INFO] [stdout] 715 | |     command: DataCommands::WorkspaceRules,
[INFO] [stdout] 716 | |     holding_type: WorkspaceRuleset,
[INFO] [stdout] 717 | |     doc: "This struct holds a vector of workspace rules per workspace"
[INFO] [stdout] 718 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: this warning originates in the macro `implement_iterators` which comes from the expansion of the macro `create_data_struct` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 33  |                 pub fn iter_mut(&mut self) -> std::slice::IterMut<'_, $holding_type> {
[INFO] [stdout]     |                                                                   +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `add_active_monitor_change_handler` found for struct `EventListener` in the current scope
[INFO] [stdout]   --> examples/events.rs:15:20
[INFO] [stdout]    |
[INFO] [stdout] 15 |     event_listener.add_active_monitor_change_handler(|state| println!("Monitor state: {state:#?}"));    
[INFO] [stdout]    |                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout] help: there is a method `add_active_monitor_changed_handler` with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 15 |     event_listener.add_active_monitor_changed_handler(|state| println!("Monitor state: {state:#?}"));    
[INFO] [stdout]    |                                             +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `add_workspace_change_handler` found for struct `EventListener` in the current scope
[INFO] [stdout]   --> examples/events.rs:16:20
[INFO] [stdout]    |
[INFO] [stdout] 16 |     event_listener.add_workspace_change_handler(|id| println!("workspace changed to {id:?}"));
[INFO] [stdout]    |                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout] help: there is a method `add_workspace_changed_handler` with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 16 |     event_listener.add_workspace_changed_handler(|id| println!("workspace changed to {id:?}"));
[INFO] [stdout]    |                                        +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0599`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `hyprland` (example "events") due to 4 previous errors
[INFO] running `Command { std: "docker" "inspect" "1e617469601fe288287862122df2840cd95402d7b76760db284e3a0da2dad7e5", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "1e617469601fe288287862122df2840cd95402d7b76760db284e3a0da2dad7e5", kill_on_drop: false }`
[INFO] [stdout] 1e617469601fe288287862122df2840cd95402d7b76760db284e3a0da2dad7e5
